Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test for valid (non-null) socket @ws in Client.reconnect() before @ws.cl... #31

Merged
merged 1 commit into from
May 29, 2015

Conversation

kachizukanne
Copy link
Contributor

Test for valid (non-null) socket @ws in Client.reconnect() before @ws.close() to avoid system failure if the bot is disabled

image

….close() to avoid system failure on disabled bot
@kachizukanne
Copy link
Contributor Author

Hi,

I reckon this update may be necessary to elegantly manage this exception. Given the trace for the call (see above image) I'm unable to trap and manage the exception from the caller

@davidkassa
Copy link

+1. Also, should this check be made on the disconnect method?

grantmd added a commit that referenced this pull request May 29, 2015
Test for valid (non-null) socket @ws in Client.reconnect() before @ws.cl...
@grantmd grantmd merged commit deee924 into slackapi:master May 29, 2015
aoberoi added a commit to aoberoi/node-slack-sdk that referenced this pull request Mar 20, 2019
tests that when propogateErrors is used, no error is emitted
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants